Yazılım Süreç Geliştirme Modellerinin KOBİ’lerde Kabulü için Model Geliştirilmesi: Ön Bulgular

The software industry is playing a significant role in development of economies all over the world. It is mainly made up of small and medium software enterprises (SMEs). These companies aim to benefit from Software Process Improvements (SPI) to increase product quality and productivity in a competitive environment. Several SPI models and frameworks have been developed to improve software quality in SMEs. As SPI require organizational change and adaptation to new tools, techniques and work practices; organizations have to handle with several challenges emerged from the change. In this study, we present the factors that influence the success and adoption of the SPI models and/or standards used in SMEs. We also present the preliminary findings of the SPI acceptance model that we developed based on an established behavioral theory for SMEs. A pilot survey study was conducted to analyze the model with 20 participants who work in a CMMI Level 3 company.Yazılım endüstrisi tüm dünya ekonomilerinin gelişiminde önemli bir rol oynamaktadır. Bu firmaların çoğunluğu küçük ve orta ölçekli şirketlerden (KOBİ) oluşmaktadır. Bu şirketler, rekabetçi bir ortamda ürün kalitesini ve verimliliğini artırmak için Yazılım Süreç İyileştirmelerinden (YSİ) faydalanmayı amaçlamaktadır. YSİ uygulamaları beraberinde kurumsal değişim ve yeni araçlara, tekniklere ve iş uygulamalarına adapte olmayı gerektirdiğinden; kurumlar değişimden kaynaklanan çeşitli zorluklarla başa çıkmak zorundadır. Bu çalışmada, KOBİ’lerde kullanılan YSİ model ve / veya standartlarının başarısını ve benimsenmesini etkileyen faktörler sunulmaktadır. Ayrıca, KOBİ’ler için Davranışsal Teoriye dayanarak geliştirdiğimiz YSİ kabul modelinin ön bulguları sunulmaktadır. CMMI Seviye 3 firmasında çalışan 20 katılımcı ile modeli analiz etmek için pilot bir anket çalışması yapılmıştır

Analysis of Software Process Improvement Activities in SMEs: A Systematic Literature Review

This Software industry is a very significant cog in today’s economic landscape. The majority of these organizations mainly comprise small and medium enterprises (SMEs). These enterprises aim to benefit from Software Process Improvement (SPI) activities in producing high-quality products and services in competitive business environments. For this purpose, SPI models have been developed for specific SME characteristics. In this study, we performed a systematic literature review to analyze the characteristics of these SPI models, the challenges of performing SPI activities in SMEs, and the critical success factors for SPI activities. In this context, 61 articles published from 2007 to 2020 were examined, as a result, 28 SPI models used in SMEs were found out. In addition, ten different situations that make SPI implementations challenging in SMEs and seven factors that affect the success of SPI studies in SMEs were reported

Assessing Software Processes over a New Generic Software Process Assessment Tool

Performing process improvement to deliver qualified products with the expected cost on time has been a requirement for organizations targeting to be successful in the software market. Software organizations usually perform process improvement based on well-known process assessment frameworks such as CMMI and ISO/IEC 15504. A number of derivatives of CMMI and ISO/IEC 15504 have been developed and they are being updated. As a result of this, the software process assessment tool based on them needs to be updated. Process assessment requires judgment and there is an unavoidable manual work. However, there are also opportunities for assessment automation. Therefore, there is a need for a generic software process assessment tool to define process assessment models and facilitate assessment. The existing tools do not meet the expected features of a software process assessment tool completely, as they have generally been developed for single process assessment models. In this study, we present GSPA, a generic software process assessment tool, which has been developed to support all structured process assessment models with its generic framework, facilitate assessment, support parallel assessment and present the reports in a well-structured way to the assessors. A multiple case study has been conducted to measure the sufficiency and the contributions of the tool

Çevik olgunluk modeli ve çeviklik değerlendirme aracı

TÜBİTAK EEEAG Proje01.04.2016The main purpose of the research project was to develop an agility maturity model and a toolbox in order to carry out agile software development processes compatible with manifesto for agile software development in software organizations in an effective and integrated way. “Agility maturity model” is defined as “agility assessment reference model” in such a way that the properties its name provides remain the same. In the scope of the project, the studies conducted are as follows: a) Development of AgilityMod agility assessment reference model: For the development of the model, the meta-structure of ISO 15504 process assessment reference models is taken as basis. Instead of process structure and practices of ISO 15504, new aspects and special practices are defined. Therefore, the model is suitable for agile process architecture and includes all components which are necessary for any assessment model. b) Development of assessment software: In order to facilitate and popularize the AgilityMod, a software is developed. c) Validation of the model in software organizations: AgilityMod is applied with the case studies in 9 different organizations and positive feedbacks are gathered. d) Introduction of the model in national and international conferences: The studies conducted during the project were published as 3 international conferences papers and presented in an educational workshop of a national conference. Additionally, 1 of the studies is accepted to be published in an international journal in 2016 and 2 of the studies are accepted to be presented in two international conferences

Catching up with Method and Process Practice: An Industry-Informed Baseline for Researchers

Software development methods are usually not applied by the book.companies are under pressure to continuously deploy software products that meet market needs and stakeholders\u27 requests. To implement efficient and effective development processes, companies utilize multiple frameworks, methods and practices, and combine these into hybrid methods. A common combination contains a rich management framework to organize and steer projects complemented with a number of smaller practices providing the development teams with tools to complete their tasks. In this paper, based on 732 data points collected through an international survey, we study the software development process use in practice. Our results show that 76.8% of the companies implement hybrid methods.company size as well as the strategy in devising and evolving hybrid methods affect the suitability of the chosen process to reach company or project goals. Our findings show that companies that combine planned improvement programs with process evolution can increase their process\u27 suitability by up to 5%

Fonksiyonel benzerliklerin fonksiyonel büyüklük ve yazılım geliştirme işgücü arasındaki ilişkiye olan etkisi.

In this study, we identified one of the reasons of the low correlation between functional size and development effort which is overlooking the similarity of the functions during the mapping of the functional size and development effort. We developed a methodology (SiRFuS) that is based on the idea of the reuse of the similar functions internally to provide high correlation between functional size and development effort. The method is developed for the identification of the similar functions based on the method of Santillo and Abran. Similarity percentages among the functional processes and Similarity Reflective Functional Sizes are computed to attain adjusted functional sizes. The similarity reflective functional sizes were named as Discrete Similarity Reflective Functional Size and Continuous Similarity Reflective Functional Size based on the characteristics of the adjusted functional sizes. The SiRFuS method consists of three stages: measurement of the software product with COSMIC Functional Size Measurement (FSM) method; identification of the functional similarities bases on the measurement results and calculation of the similarity reflective functional sizes. In order to facilitate the detection of similar functions, calculation of the percentage of the similarities and similarity reflective functional sizes; a software tool is developed based on the SiRFuS method. Two case studies were performed in order to identify the improvement opportunities and evaluate the applicability of the method and the tool.M.S. - Master of Scienc

Agilitymod: çeviklik değerlendirme için bir yazılım çeviklik referans modeli.

Agile software development methodologies have gained significant interest in IT community proposing solutions to problems of traditional, plan-driven software development approaches. However, not every organization that tries to adopt agile methods succeeds, that is mostly because practitioners misinterpret the agile values, principles or practices during the adoption and transformation or see a single agile method as a complete solution to all problems. There is a gap in the field to assist software organizations in assessing their agility levels and introducing roadmaps in adopting agile principles/practices. In this thesis study we propose a Software Agility Assessment Reference Model that will be used for assessing organizations’ position in agility and indicating the gaps that prevents fully obtaining the benefits of agile software development and providing roadmaps to roadmaps to organizations in adopting agile principles/practices. The model is based on the meta-model structure of ISO/IEC 15504-Process Assessment Standard to create a common basis for performing assessments of agility and present the assessment results using a common rating scale. We performed exploratory case studies and obtained the opinions of the experts to improve the Model. Validation of the proposed model is achieved through one of the qualitative research methods, case studies. We performed a multiple case study including six cases for validation.Ph.D. - Doctoral Progra

To what extent the medical device software regulations can be achieved with agile software development methods? XP—DSDM—Scrum

For medical device software development organisations, it is very challenging to maintain both conformance to the strict regulatory requirements enforced by the safety critical nature of the domain and achieve efficiency in software development. Agile software development methods provide promising solutions to overcome the efficiency issues and the challenges of traditional software development approaches in the domain. Previously, we investigated to what extent the regulatory requirements defined in MDevSPICE® (the software process assessment framework for medical device software development) are met through using XP (eXtreme Programming) and Scrum and what additional practices have to be performed to ensure safety and regulatory compliance in the medical device software development domain. In this paper, we extended the research to include the Dynamic Systems Development Method (DSDM) which covers the whole software development life cycle. Here, we provide a comprehensive and quantitative analysis of XP’s and DSDM’s suitability for medical device software development and briefly discuss Scrum from the same perspective. We provide the coverage ratios of processes and practices defined in MDevSPICE® when these agile software development methods are implemented

A Reference Model for Software Agility Assessment: AgilityMod

In this paper, we present AgilityMod that we developed with the purpose of identifying agility levels of software development projects, indicating agility gaps and providing roadmaps to organizations in adopting agile principles/practices. AgilityMod shares the meta-model structure of ISO/IEC 15504, software process assessment model, however, it differentiates from ISO/IEC 15504 in terms of its process architecture, process descriptions and description of other model elements. In this paper, we focus on the structure of the Model and describe the development stages of the Model. In addition, we briefly present a multiple case study that included eight cases, which was conducted to identify applicability and suitability of the Model

Assessment of agile maturity models: a multiple case study

Agile methods are welcomed by software community in recent years. The move from traditional methods to agile methods is not straightforward. Software organizations need assistance to achieve transition from traditional software development approaches to agile approaches and to improve their agile capability. During the last few years several agile maturity models/frameworks are developed to guide organizations in agile process improvement and agile adoption. In this study, we assess the strengths and weaknesses of agile maturity models/frameworks from agile process assessment and agile process improvement perspectives. To assess the models we have applied the models in a selected software organization. We discuss the strengths and weakness of each model and provide suggestions for their utilization